Skip to content

Add “Report a Problem” button to pause screen#2081

Merged
wjt merged 2 commits intomainfrom
wjt/add-report-a-problem-button-to-pause-screen
Mar 25, 2026
Merged

Add “Report a Problem” button to pause screen#2081
wjt merged 2 commits intomainfrom
wjt/add-report-a-problem-button-to-pause-screen

Conversation

@wjt
Copy link
Copy Markdown
Member

@wjt wjt commented Mar 25, 2026

This opens your browser at a bug report form, with the game version and current scene pre-filled into the appropriate fields. This does mean you need a GitHub account to report a problem. In future you could imagine directing users somewhere else, but this is an simple start based on infrastructure that already exists.

To do this, refactor the code that determines the version from git describe so that it can also be used when running the game from the editor. For good measure, put the version number on the pause screen too.

Resolves #2080

@wjt wjt requested a review from a team as a code owner March 25, 2026 09:55
@github-actions
Copy link
Copy Markdown

Play this branch at https://play.threadbare.game/branches/endlessm/wjt/add-report-a-problem-button-to-pause-screen/.

(This launches the game from the start, not directly at the change(s) in this pull request.)

This opens your browser at a bug report form, with the game version and
current scene pre-filled into the appropriate fields. This does mean you
need a GitHub account to report a problem. In future you could imagine
directing users somewhere else, but this is an simple start based on
infrastructure that already exists.

To do this, refactor the code that determines the version from `git
describe` so that it can also be used when running the game from the
editor. For good measure, put the version number on the pause screen
too.

Resolves #2080
@wjt wjt force-pushed the wjt/add-report-a-problem-button-to-pause-screen branch from ac0585c to 11f4a3e Compare March 25, 2026 10:00
@wjt
Copy link
Copy Markdown
Member Author

wjt commented Mar 25, 2026

This uses the form fields added in:

@manuq
Copy link
Copy Markdown
Collaborator

manuq commented Mar 25, 2026

This is great! It prefills the version and affected scene.
image

Maybe is too much of an assumption that the affected scene is the current one. The player might see a problem, then move on and later decide to report. I think we can clarify this in the bug report form itself. Something like "this may be prefilled if you clicked Report a problem in the game menu, with the current scene". Is great to have the current scene prefilled, don't get me wrong.

@wjt wjt requested a review from a team as a code owner March 25, 2026 14:26
Comment on lines +29 to +34
Give an example of a scene in the game where you see this problem. If
you're not sure, describe the scene visually, or leave this blank.

If you report a problem from within the game, this will have been filled
automatically with the current scene. You can change this if you are
reporting a problem you saw in a different scene.
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@manuq Do you think this change captures your point?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wjt yes, well explained!

@wjt wjt merged commit f235bfd into main Mar 25, 2026
6 checks passed
@wjt wjt deleted the wjt/add-report-a-problem-button-to-pause-screen branch March 25, 2026 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add in-game problem reporting

2 participants